Temporarily exclude linux32 from CI #3022
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
linux32 nightlies are stuck at
commit 5b2a4b1e45 (2022-02-13 06:27 UTC)and as far as I know, will likely be for a while yet.This blocks merging PRs that need changes in the base repo like #2793 and #3021
So I'm proposing excluding linux32 from CI until nightlies recover
We have Pkg tests run on Base now for linux32, I believe.. so regressions will be picked up after updating the Pkg commit in base
cc. @staticfloat @DilumAluthge